I am seeing an...
I am seeing an issue with one of our operations in that the user scans the locator barcode, but the mobile device actually posts a different location to the WMS. The "shift" in the locator entered is random, though a recent example occured where the user scanned the locator for location 201601.. and the transaction confirmed the locator as 111601..
The barcodes are confirmed correct in their construction, and use the "21L" data identifier for the locator.
The users are using the WMS Mobile Interface and the devices are Motorola MC-9090s. From pictures I have, I see the "To Loc" field populated with the scanned locator, but the "Confirm" field is completely different.
We are trying to devise possible causes and solutions right now. Any experience with similar issues would be greatly appreciated
Is this happening for some
Is this happening for some transactions???
I am not sure if there is anything wrong except understanding the functionality
As per my understanding the TO LOC and TO SUB are defaulted by the system (by Put away rule/Item-transaction default).
After that you need to tab into the confirm field in mobile device and then scan the locator (and if you are using locator alias then the user need to enter the locator alias as well)
Am I correct??